Elm Syntax Highlighting
Syntax Highlighting for Elm in Sublime Text
Details
Installs
- Total 29K
- Win 9K
- Mac 15K
- Linux 6K
Mar 22 | Mar 21 | Mar 20 | Mar 19 | Mar 18 | Mar 17 | Mar 16 | Mar 15 | Mar 14 | Mar 13 | Mar 12 | Mar 11 | Mar 10 | Mar 9 | Mar 8 | Mar 7 | Mar 6 | Mar 5 | Mar 4 | Mar 3 | Mar 2 | Mar 1 | Feb 28 | Feb 27 | Feb 26 | Feb 25 | Feb 24 | Feb 23 | Feb 22 | Feb 21 | Feb 20 | Feb 19 | Feb 18 | Feb 17 | Feb 16 | Feb 15 | Feb 14 | Feb 13 | Feb 12 | Feb 11 | Feb 10 | Feb 9 | Feb 8 | Feb 7 | Feb 6 | Feb 5 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 2 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 |
Mac | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 2 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 2 |
Linux | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
Elm Syntax Highlighting
Just add syntax highlighting for Elm.
Install Instructions
Recommended Workflow
I do all of my Elm development with Terminal and Sublime Text open next to each other like this:
I mostly focus on the code in Sublime Text.
When I am curious if things work, I switch to Terminal and run something like elm make src/Main.elm
to see if I get any errors.
Then I switch back to Sublime Text and use Ctrl-t (or Cmd-t on Mac) to navigate to the relevant files and make any fixes.
Workflow Benefits
The recommended workflow has some underappreciated benefits:
- Fast - Never wait for a slow editor. No background tasks eating RAM and CPU.
- Flexibile - Some projects needs more than an
elm make
call. I can switch toelm reactor
or a custom./build.sh
script and keep essentially the same workflow. - Robust - Not much can go wrong here, so I never spend time messing with integrations. Changes in
elm
,elm-test
, orelm-format
are only a concern in the terminal.
I really love this balance! It has that particular character of focused designs.
That said, I know some people want a bit more, so I made elm-format-on-save
as well. It may be worth setting this up once you have been happily using Elm for a while and become curious what it might be like to use Elm at work.